docs(findings): mark F6 json-render NG0956 residual resolved#682
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the F6 residual NG0956 follow-up.
Re-grounded against current main (post #680 render-lifecycle rework + F4 + the markdown
\$indexfixes): every@forin the json-render path (cockpit/ag-ui/json-render views, a2ui catalog, libs/render core, libs/chat markdown) now keys on a primitive (\$index/string key/value) — the NG0956-pronetrack <object>pattern is gone. Confirmed by a livecockpit-ag-ui-json-rendere2e run streaming the airline dashboard: zero NG0956.No regression guard committed: an e2e console-guard was prototyped but proven ineffective — a negative control (forcing
track [key]on the fixture-renderedcontainerview) produced no NG0956, because aimock fixture replay delivers the spec ~atomically so no@forre-materializes. A real guard would need a component-level vitest test feeding successive specs (deferred as optional).Docs-only.
🤖 Generated with Claude Code